Management of near field communications using low power modes of an electronic device

ABSTRACT

Systems, methods, and computer-readable media for managing near field communications during a low power management mode of an electronic device are provided that may make credentials of a near field communication (“NFC”) component appropriately secure and appropriately accessible while also limiting the power consumption of the NFC component and of other components of the electronic device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/063,433, filed Oct. 25, 2013 (now U.S. Pat. No. 9,603,090), whichclaims the benefit of prior filed U.S. Provisional Patent ApplicationNo. 61/863,549, filed Aug. 8, 2013, each of which is hereby incorporatedby reference herein in its entirety.

TECHNICAL FIELD

This disclosure relates to the management of near field communicationsand, more particularly, to the management of near field communicationsusing low power modes of an electronic device.

BACKGROUND OF THE DISCLOSURE

Portable electronic devices (e.g., cellular telephones) may be providedwith near field communication (“NFC”) components for enablingcontactless proximity-based communications with another entity. Oftentimes, these communications are associated with currency transactions orother secure data transactions that users rely on every day, such ascredit card payments and public transportation ticketing. However, dueto the limited amount of power available to battery operated devices,the NFC capabilities of such devices are often compromised or renderedunusable when their available power drops below certain thresholds.

SUMMARY OF THE DISCLOSURE

This document describes systems, methods, and computer-readable mediafor managing power usage in a device that is capable of near fieldcommunications and/or other wireless communications technologies.

For example, a method for operating an electronic device may includereceiving authentication information using an input component of theelectronic device. The method may also include powering at least a firstportion of a near field communication component of the electronic devicebased on the received authentication information.

As another example, a method of operating an electronic device mayinclude detecting a low power mode initiation event. In response to thedetecting, the method may also include disabling an active element ofthe electronic device, where the active element includes at least one ofa communications component and an output component. The method alsoincludes closing at least one active application that was running on theelectronic device prior to the detecting, and running a low power modeapplication on the electronic device. Running the low power modeapplication may include receiving authentication information from aninput component of the electronic device and enabling a near fieldcommunication component of the electronic device based on the receivedauthentication information.

As yet another example, a method of operating an electronic device mayinclude detecting a low power mode initiation event. In response to thedetecting, the method may also include disabling an element of theelectronic device and identifying an authentication initiation event. Inresponse to the identifying, the method may also include providing on anoutput component of the electronic device an output that requests userinteraction for the enablement of a near field communication componentof the electronic device.

As yet another example, a non-transitory computer-readable medium mayinclude computer-readable instructions recorded thereon for detecting alow power mode initiation event on an electronic device and, in responseto the detecting, disabling an element of the electronic device,identifying an authentication initiation event on the electronic device,and, in response to the identifying, providing on an output component ofthe electronic device an output that requests the enablement of a nearfield communication component of the electronic device.

As yet another example, an electronic device may include a near fieldcommunication component, an output component, and a processor. Theprocessor may be configured to detect a low power mode initiation event,ensure that at least one function of the near field communicationcomponent is disabled in response to the detection of the low power modeinitiation event, identify an authentication initiation event once it isensured that the at least one function of the near field communicationcomponent is disabled, and, in response to the identification of theauthentication initiation event, provide on the output component anoutput that requests user interaction with the electronic device for theenablement of the at least one function of the near field communicationcomponent.

This Summary is provided merely to summarize some example embodiments,so as to provide a basic understanding of some aspects of the subjectmatter described in this document. Accordingly, it will be appreciatedthat the features described in this Summary are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The discussion below makes reference to the following drawings, in whichlike reference characters may refer to like parts throughout, and inwhich:

FIG. 1 is a schematic view of an illustrative communications system thatincludes an electronic device for managing near field communications;

FIG. 2 is a front view of the electronic device of FIG. 1;

FIG. 3 is a schematic view of an illustrative portion of the electronicdevice of FIGS. 1 and 2;

FIGS. 4A-4G are front views of screens of a graphical user interface ofthe electronic device of FIGS. 1-3 illustrating processes for managingnear field communications; and

FIGS. 5-8 are flowcharts of illustrative processes for managing nearfield communications.

DETAILED DESCRIPTION OF THE DISCLOSURE

Near field communications may be managed differently according todifferent power management modes of an electronic device. In certain lowpower management modes, certain components of an electronic device maybe at least partially disabled or shut down to conserve power. When anelectronic device operates in these modes, credentials of an NFCcomponent in the device may be appropriately secure and/or appropriatelyaccessible, while power consumption of the NFC component is limited orreduced. For example, when entering a low power management mode, an NFCcomponent may be initially disabled and user authentication may berequired to re-enable the NFC component for use during the low powermanagement mode. An output component, such as a display, may also beinitially disabled upon entering the low power management mode, yet theoutput component may be re-enabled at some later point during the lowpower management mode in order to prompt a user to authenticate himselfor herself such that the NFC component may be re-enabled. One or moreapplications, such as all non-native applications, running on the deviceprior to entering the low power management mode may be disabled uponentering the low power management mode and a specific low powermanagement mode application may be launched to control the operation ofthe NFC component and/or any other components of the electronic deviceduring the low power management mode. The low power management mode maybe initialized in response to a user request or in response to theremaining power of a power supply dropping below a specific threshold,whereas user authentication of the NFC component during the low powermanagement mode may be initialized in response to a user request or inresponse to an NFC terminal being detected within a specific proximityof the electronic device.

FIG. 1 is a schematic view of an illustrative communications system 1that may include a terminal 10 and an electronic device 100 for managingnear field communications 55 with terminal 10 in accordance with someembodiments. Electronic device 100 can include, but is not limited to, amusic player (e.g., an iPod™ available by Apple Inc. of Cupertino,Calif.), video player, still image player, game player, other mediaplayer, music recorder, movie or video camera or recorder, still camera,other media recorder, radio, medical equipment, domestic appliance,transportation vehicle instrument, musical instrument, calculator,cellular telephone (e.g., an iPhone™ available by Apple Inc.), otherwireless communication device, personal digital assistant, remotecontrol, pager, computer (e.g., a desktop, laptop, tablet (e.g., aniPad™ available by Apple Inc.), server, etc.), monitor, television,stereo equipment, set up box, set-top box, boom box, modem, router,printer, or any combination thereof. In some embodiments, electronicdevice 100 may perform a single function (e.g., a device dedicated tomanaging near field communications) and, in other embodiments,electronic device 100 may perform multiple functions (e.g., a devicethat manages near field communications, plays music, and receives andtransmits telephone calls).

Electronic device 100 may be any portable, mobile, hand-held, orminiature electronic device that may be configured to manage near fieldcommunications wherever a user travels. Some miniature electronicdevices may have a form factor that is smaller than that of hand-heldelectronic devices, such as an iPod™. Illustrative miniature electronicdevices can be integrated into various objects that may include, but arenot limited to, watches, rings, necklaces, belts, accessories for belts,headsets, accessories for shoes, virtual reality devices, glasses, otherwearable electronics, accessories for sporting equipment, accessoriesfor fitness equipment, key chains, or any combination thereof.Alternatively, electronic device 100 may not be portable at all, but mayinstead be generally stationary.

As shown in FIG. 1, for example, electronic device 100 may include aprocessor 102, memory 104, communications component 106, power supply108, input component 110, output component 112, antenna 116, and nearfield communication (“NFC”) component 120. Electronic device 100 mayalso include a bus 118 that may provide one or more wired or wirelesscommunication links or paths for transferring data and/or power to,from, or between various other components of device 100. In someembodiments, one or more components of electronic device 100 may becombined or omitted. Moreover, electronic device 100 may include othercomponents not combined or included in FIG. 1. For example, electronicdevice 100 may include motion-sensing circuitry, a compass, any othersuitable components, or several instances of the components shown inFIG. 1. For the sake of simplicity, only one of each of the componentsis shown in FIG. 1.

Memory 104 may include one or more storage mediums, including forexample, a hard-drive, flash memory, permanent memory such as read-onlymemory (“ROM”), semi-permanent memory such as random access memory(“RAM”), any other suitable type of storage component, or anycombination thereof. Memory 104 may include cache memory, which may beone or more different types of memory used for temporarily storing datafor electronic device applications. Memory 104 may be fixedly embeddedwithin electronic device 100 or may be incorporated onto one or moresuitable types of cards that may be repeatedly inserted into and removedfrom electronic device 100 (e.g., a subscriber identity module (“SIM”)card or secure digital (“SD”) memory card). Memory 104 may store mediadata (e.g., music and image files), software (e.g., for implementingfunctions on device 100), firmware, preference information (e.g., mediaplayback preferences), lifestyle information (e.g., food preferences),exercise information (e.g., information obtained by exercise monitoringequipment), transaction information (e.g., information such as creditcard information), wireless connection information (e.g., informationthat may enable device 100 to establish a wireless connection),subscription information (e.g., information that keeps track of podcastsor television shows or other media a user subscribes to), contactinformation (e.g., telephone numbers and e-mail addresses), calendarinformation, any other suitable data, or any combination thereof.

Communications component 106 may be provided to allow device 100 tocommunicate with one or more other electronic devices or servers usingany suitable communications protocol. For example, communicationscomponent 106 may support Wi-Fi (e.g., an 802.11 protocol), ZigBee(e.g., an 802.15.4 protocol), WiDi™, Ethernet, Bluetooth™, Bluetooth™Low Energy (“BLE”), high frequency systems (e.g., 900 MHz, 2.4 GHz, and5.6 GHz communication systems), infrared, transmission controlprotocol/internet protocol (“TCP/IP”) (e.g., any of the protocols usedin each of the TCP/IP layers), Stream Control Transmission Protocol(“SCTP”), Dynamic Host Configuration Protocol (“DHCP”), hypertexttransfer protocol (“HTTP”), BitTorrent™, file transfer protocol (“FTP”),real-time transport protocol (“RTP”), real-time streaming protocol(“RTSP”), real-time control protocol (“RTCP”), Remote Audio OutputProtocol (“RAOP”), Real Data Transport Protocol™ (“RDTP”), User DatagramProtocol (“UDP”), secure shell protocol (“SSH”), wireless distributionsystem (“WDS”) bridging, any communications protocol that may be used bywireless and cellular telephones and personal e-mail devices (e.g.,Global System for Mobile Communications (“GSM”), GSM plus Enhanced Datarates for GSM Evolution (“EDGE”), Code Division Multiple Access(“CDMA”), Orthogonal Frequency-Division Multiple Access (“OFDMA”), highspeed packet access (“HSPA”), multi-band, etc.), any communicationsprotocol that may be used by a low power Wireless Personal Area Network(“6LoWPAN”) module, any other communications protocol, or anycombination thereof. Communications component 106 may also include or beelectrically coupled to any suitable transceiver circuitry (e.g.,transceiver circuitry or antenna 116 via bus 118) that can enable device100 to be communicatively coupled to another device (e.g., a hostcomputer or an accessory device) and communicate with that other devicewirelessly, or via a wired connection (e.g., using a connector port).Communications component 106 may be configured to determine ageographical position of electronic device 100. For example,communications component 106 may utilize the global positioning system(“GPS”) or a regional or site-wide positioning system that may use celltower positioning technology or Wi-Fi technology.

Power supply 108 can include any suitable circuitry for receiving and/orgenerating power, and for providing such power to one or more of theother components of electronic device 100. For example, power supply 108can be coupled to a power grid (e.g., when device 100 is not acting as aportable device or when a battery of the device is being charged at anelectrical outlet with power generated by an electrical power plant). Asanother example, power supply 108 can be configured to generate powerfrom a natural source (e.g., solar power using solar cells). As anotherexample, power supply 108 can include one or more batteries forproviding power (e.g., when device 100 is acting as a portable device).For example, power supply 108 can include one or more of a battery(e.g., a gel, nickel metal hydride, nickel cadmium, nickel hydrogen,lead acid, or lithium-ion battery), an uninterruptible or continuouspower supply (“UPS” or “CPS”), and circuitry for processing powerreceived from a power generation source (e.g., power generated by anelectrical power plant and delivered to the user via an electricalsocket or otherwise). The power can be provided by power supply 108 asalternating current or direct current, and may be processed to transformpower or limit received power to particular characteristics. Forexample, the power can be transformed to or from direct current, andconstrained to one or more values of average power, effective power,peak power, energy per pulse, voltage, current (e.g., measured inamperes), or any other characteristic of received power. Power supply108 can be operative to request or provide particular amounts of powerat different times, for example, based on the needs or requirements ofelectronic device 100 or periphery devices that may be coupled toelectronic device 100 (e.g., to request more power when charging abattery than when the battery is already charged).

One or more input components 110 may be provided to permit a user tointeract or interface with device 100. For example, input component 110can take a variety of forms, including, but not limited to, a touch pad,dial, click wheel, scroll wheel, touch screen, one or more buttons(e.g., a keyboard), mouse, joy stick, track ball, microphone, camera,scanner (e.g., a bar code scanner or any other suitable scanner that mayobtain product identifying information from a code, such as a bar code,a QR code, or the like), proximity sensor, light detector, motionsensor, biometric sensor (e.g., a fingerprint reader or other featurerecognition sensor, which may operate in conjunction with afeature-processing application that may be accessible to electronicdevice 100 for authenticating a user), and combinations thereof. Eachinput component 110 can be configured to provide one or more dedicatedcontrol functions for making selections or issuing commands associatedwith operating device 100.

Electronic device 100 may also include one or more output components 112that may present information (e.g., graphical, audible, and/or tactileinformation) to a user of device 100. For example, output component 112of electronic device 100 may take various forms, including, but notlimited to, audio speakers, headphones, audio line-outs, visualdisplays, antennas, infrared ports, rumblers, vibrators, or combinationsthereof.

As a specific example, electronic device 100 may include a displayoutput component as output component 112. Such a display outputcomponent may include any suitable type of display or interface forpresenting visual data to a user. A display output component may includea display embedded in device 100 or coupled to device 100 (e.g., aremovable display). A display output component may include, for example,a liquid crystal display (“LCD”), a light emitting diode (“LED”)display, an organic light-emitting diode (“OLED”) display, asurface-conduction electron-emitter display (“SED”), a carbon nanotubedisplay, a nanocrystal display, any other suitable type of display, orcombination thereof. Alternatively, a display output component caninclude a movable display or a projecting system for providing a displayof content on a surface remote from electronic device 100, such as, forexample, a video projector, a head-up display, or a three-dimensional(e.g., holographic) display. As another example, a display outputcomponent may include a digital or mechanical viewfinder, such as aviewfinder of the type found in compact digital cameras, reflex cameras,or any other suitable still or video camera. A display output componentmay include display driver circuitry, circuitry for driving displaydrivers, or both, and such a display output component can be operativeto display content (e.g., media playback information, applicationscreens for applications implemented on electronic device 100,information regarding ongoing communications operations, informationregarding incoming communications requests, device operation screens,etc.) that may be under the direction of processor 102.

It should be noted that one or more input components and one or moreoutput components may sometimes be referred to collectively herein as aninput/output (“I/O”) component or I/O interface (e.g., input component110 and output component 112 as I/O component or I/O interface 114). Forexample, input component 110 and output component 112 may sometimes be asingle I/O component 114, such as a touch screen, that may receive inputinformation through a user's touch of a display screen and that may alsoprovide visual information to a user via that same display screen.

Processor 102 of electronic device 100 may include any processingcircuitry that may be operative to control the operations andperformance of one or more components of electronic device 100. Forexample, processor 102 may receive input signals from input component110 and/or drive output signals through output component 112. As shownin FIG. 1, processor 102 may be used to run one or more applications,such as an application 103. Application 103 may include, but is notlimited to, one or more operating system applications, firmwareapplications, media playback applications, media editing applications,NFC low power mode applications, biometric feature-processingapplications, or any other suitable applications. For example, processor102 may load application 103 as a user interface program to determinehow instructions or data received via an input component 110 or othercomponent of device 100 may manipulate the way in which information maybe stored and/or provided to the user via an output component 112.Application 103 may be accessed by processor 102 from any suitablesource, such as from memory 104 (e.g., via bus 118) or from anotherdevice or server (e.g., via communications component 106). Processor 102may include a single processor or multiple processors. For example,processor 102 may include at least one “general purpose” microprocessor,a combination of general and special purpose microprocessors,instruction set processors, graphics processors, video processors,and/or related chips sets, and/or special purpose microprocessors.Processor 102 also may include on board memory for caching purposes.

Electronic device 100 may also include near field communication (“NFC”)component 120. NFC component 120 may be any suitable proximity-basedcommunication mechanism that may enable contact-less transactions orcommunications 55 between electronic device 100 and terminal 10 (e.g., apayment terminal). NFC component 120 may allow for close rangecommunication at relatively low data rates (e.g., 424 kbps), and maycomply with any suitable standards, such as ISO/IEC 7816, ISO/IEC 18092,ECMA-340, ISO/IEC 21481, ECMA-352, ISO 14443, and/or ISO 15693.Alternatively or additionally, NFC component 120 may allow for closerange communication at relatively high data rates (e.g., 560 Mbps), andmay comply with any suitable standards, such as the TransferJet™protocol. Communication between NFC component 120 and terminal 10 mayoccur within any suitable close range distance D between device 100 andterminal 10, such as a range of approximately 2 to 4 centimeters, andmay operate at any suitable frequency (e.g., 13.56 MHz). For example,such close range communication of NFC component 120 may take place viamagnetic field induction, which may allow NFC component 120 tocommunicate with other NFC devices and/or to retrieve information fromtags having radio frequency identification (“RFID”) circuitry. NFCcomponent 120 may provide a manner of acquiring merchandise information,transferring payment information, and otherwise communicating with anexternal device (e.g., terminal 10).

NFC component 120 may include any suitable modules for enablingcontactless proximity-based communication 55 between electronic device100 and terminal 10. As shown in FIG. 1, for example, NFC component 120may include an NFC device module 130, an NFC controller module 140, andan NFC memory module 150.

NFC device module 130 may include an NFC data module 132, an NFC antenna134, and an NFC booster 136. NFC data module 132 may be configured tocontain, route, or otherwise provide any suitable data that may betransmitted by NFC component 120 to terminal 10 as part of a contactlessproximity-based or NFC communication 55. Additionally or alternatively,NFC data module 132 may be configured to contain, route, or otherwisereceive any suitable data that may be received by NFC component 120 fromterminal 10 as part of a contactless proximity-based communication 55.

NFC transceiver or NFC antenna 134 may be any suitable antenna or othersuitable transceiver circuitry that may generally enable communicationof communication 55 from NFC data module 132 to terminal 10 and/or toNFC data module 132 from terminal 10. Therefore, NFC antenna 134 (e.g.,a loop antenna) may be provided specifically for enabling thecontactless proximity-based communication capabilities of NFC component120.

Alternatively or additionally, NFC component 120 may utilize the sametransceiver circuitry or antenna (e.g., antenna 116) that anothercommunication component of electronic device 100 (e.g., communicationcomponent 106) may utilize. For example, communication component 106 mayleverage antenna 116 to enable Wi-Fi, Bluetooth™, or GPS communicationbetween electronic device 100 and another remote entity, while NFCcomponent 120 may leverage antenna 116 to enable contactlessproximity-based or NFC communication 55 between NFC data module 132 ofNFC device module 130 and another entity (e.g., terminal 10). In suchembodiments, NFC device module 130 may include NFC booster 136, whichmay be configured to provide appropriate signal amplification for dataof NFC component 120 (e.g., data within NFC data module 132) so thatsuch data may be appropriately transmitted by shared antenna 116 ascommunication 55 to terminal 10. For example, shared antenna 116 mayrequire amplification from booster 136 before antenna 116 (e.g., anon-loop antenna) may be properly enabled for communicating contactlessproximity-based or NFC communication 55 between electronic device 100and terminal 10 (e.g., more power may be needed to transmit NFC datausing antenna 116 than may be needed to transmit other types of datausing antenna 116).

NFC controller module 140 may include at least one NFC processor module142. NFC processor module 142 may operate in conjunction with NFC devicemodule 130 to enable, activate, allow, and/or otherwise control NFCcomponent 120 for communicating NFC communication 55 between electronicdevice 100 and terminal 10. NFC processor module 142 may exist as aseparate component, may be integrated into another chipset, or may beintegrated with processor 102, for example, as part of a system on achip (“SoC”). As shown in FIG. 1, NFC processor module 142 of NFCcontroller module 140 may be used to run one or more applications, suchas an NFC low power mode or wallet application 143 that may help dictatethe function of NFC component 120. Application 143 may include, but isnot limited to, one or more operating system applications, firmwareapplications, NFC low power applications, or any other suitableapplications that may be accessible to NFC component 120 (e.g.,application 103). NFC controller module 140 may include one or moreprotocols, such as the Near Field Communication Interface and Protocols(“NFCIP-1”), for communicating with another NFC device (e.g., terminal10). The protocols may be used to adapt the communication speed and todesignate one of the connected devices as the initiator device thatcontrols the near field communication.

NFC controller module 140 may control the near field communication modeof NFC component 120. For example, NFC processor module 142 may beconfigured to switch NFC device module 130 between a reader/writer modefor reading information (e.g., communication 55) from NFC tags (e.g.,from terminal 10) to NFC data module 132, a peer-to-peer mode forexchanging data (e.g., communication 55) with another NFC enabled device(e.g., terminal 10), and a card emulation mode for allowing another NFCenabled device (e.g., terminal 10) to read information (e.g.,communication 55) from NFC data module 132. NFC controller module 140also may be configured to switch NFC component 120 between active andpassive modes. For example, NFC processor module 142 may be configuredto switch NFC device module 130 (e.g., in conjunction with NFC antenna134 or shared antenna 116) between an active mode where NFC devicemodule 130 may generate its own RF field and a passive mode where NFCdevice module 130 may use load modulation to transfer data to anotherdevice generating an RF field (e.g., terminal 10). Operation in such apassive mode may prolong the battery life of electronic device 100compared to operation in such an active mode. The modes of NFC devicemodule 130 may be controlled based on preferences of a user and/or basedon preferences of a manufacturer of device 100, which may be defined orotherwise dictated by an application running on device 100 (e.g.,application 103 and/or application 143).

NFC memory module 150 may operate in conjunction with NFC device module130 and/or NFC controller module 140 to allow for NEC communication 55between electronic device 100 and terminal 10. NFC memory module 150 maybe embedded within NFC device hardware or within an NFC integratedcircuit (“IC”). NFC memory module 150 may be tamper resistant and mayinclude at least a portion of a secure element. For example, NFC memorymodule 150 may store one or more applications relating to NFCcommunications (e.g., application 143) that may be accessed by NECcontroller module 140. For example, such applications may includefinancial payment applications, secure access system applications,loyalty card applications, and other applications, which may beencrypted. In some embodiments, NFC controller module 140 and NEC memorymodule 150 may independently or in combination provide a dedicatedmicroprocessor system that may contain an operating system, memory,application environment, and security protocols intended to be used tostore and execute sensitive applications on electronic device 100. NECmemory module 150 may be a portion of memory 104 or at least onededicated chip specific to NFC component 120. NFC memory module 150 mayreside on a SIM, a dedicated chip on a motherboard of electronic device100, or as an external plug in memory card. NFC memory module 150 may becompletely independent from NFC controller module 140 and may beprovided by different components of device 100 and/or provided toelectronic device 100 by different removable subsystems.

NFC memory module 150 may include one or more of an issuer securitydomain (“ISD”) 152 and a supplemental security domain (“SSD”) 154 (e.g.,a service provider security domain (“SPSD”), a trusted service managersecurity domain (“TSMSD”), etc.), which may be defined and managed by anNFC specification standard (e.g., GlobalPlatform). For example, ISD 152may be a portion of NFC memory module 150 in which a trusted servicemanager (“TSM”) or issuing financial institution may store keys and/orother suitable information for creating or otherwise provisioning one ormore credentials (e.g., credentials associated with various creditcards, bank cards, gift cards, access cards, transit passes, etc.) onelectronic device 100 (e.g., via communications component 106), forcredential content management, and/or security domain management. Aspecific supplemental security domain (“SSD”) 154 (e.g., one of SSDs154-154 b) may be associated with a specific credential (e.g., aspecific credit card credential or a specific public transit cardcredential) that may provide specific privileges or payment rights toelectronic device 100. Each SSD 154 may have its own manager key 155 forits own application or applet 153 that may need to be activated toenable a specific credential of that SSD 154 for use by NFC devicemodule 130 as an NFC communication 55. For example, a particular SSD 154may be associated with a particular credit card credential. However,that particular credential may only be communicated as an NFCcommunication 55 to terminal 10 by NFC component 120 (e.g., thatparticular credential may only be accessible by NFC data module 132)when a particular applet 153 of that particular SSD 154 has been enabledor otherwise activated or unlocked for such use. Security features maybe provided for enabling use of NFC component 120, as described below,that may be particularly useful when transmitting payment information,such as credit card information or bank account information to terminal10. Such security features also may include a secure storage area thatmay have restricted access. For example, user authentication viapersonal identification number (“PIN”) entry or via user interactionwith a biometric sensor may need to be provided to access the securestorage area. In certain embodiments, some or all of the securityfeatures may be stored within NFC memory module 150. Further, securityinformation, such as an authentication key, for communicating withterminal 10 may be stored within NFC memory module 150. In certainembodiments, NFC memory module 150 may include a microcontrollerembedded within electronic device 100.

Terminal 10 may include a reader for detecting, reading, or otherwisereceiving NFC communication 55 from electronic device 100 (e.g., whenelectronic device 100 comes within a certain distance or proximity D ofterminal 10). Accordingly, it is noted that NFC communication 55 betweenterminal 10 and electronic device 100 may occur wirelessly and, as such,may not require a clear “line of sight” between the respective devices.As mentioned, NFC device module 130 may be passive or active. Whenpassive, NFC device module 130 may only be activated when within aresponse range D of a suitable reader of terminal 10. For instance, areader of terminal 10 may emit a relatively low-power radio wave fieldthat may be used to power an antenna utilized by NFC device module 130(e.g., shared antenna 116 or NFC-specific antenna 134) and, thereby,enable that antenna to transmit suitable NFC communication information(e.g., credit card credential information) from NFC data module 132, viaantenna 116 or antenna 134, to terminal 10 as NFC communication 55. Whenactive, NFC device module 130 may incorporate or otherwise have accessto a power source local to electronic device 100 (e.g., power supply108) that may enable shared antenna 116 or NFC-specific antenna 134 toactively transmit NFC communication information (e.g., credit cardcredential information) from NFC data module 132, via antenna 116 orantenna 134, to terminal 10 as NFC communication 55, rather than reflectradio frequency signals, as in the case of a passive NFC device module130.

While NFC component 120 has been described with respect to near fieldcommunication, it is to be understood that component 120 may beconfigured to provide any suitable contactless proximity-based mobilepayment or any other suitable type of contactless proximity-basedcommunication 55 between electronic device 100 and terminal 10. Forexample, NFC component 120 may be configured to provide any suitableshort-range communication, such as those involvingelectromagnetic/electrostatic coupling technologies.

Electronic device 100 may also be provided with a housing 101 that mayat least partially enclose one or more of the components of device 100for protection from debris and other degrading forces external to device100. In some embodiments, one or more of the components may be providedwithin its own housing (e.g., input component 110 may be an independentkeyboard or mouse within its own housing that may wirelessly or througha wire communicate with processor 102, which may be provided within itsown housing).

As shown in FIG. 2, one specific example of electronic device 100 may bea handheld electronic device, such as an iPhone™, where housing 101 mayallow access to various input components 110 a-110 i, various outputcomponents 112 a-112 c, and various I/O components 114 a-114 d throughwhich device 100 and a user and/or an ambient environment may interfacewith each other. Input component 110 a may include a button that, whenpressed, may cause a “home” screen or menu of a currently runningapplication to be displayed by device 100. Input component 100 b may bea button for toggling electronic device 100 between a sleep mode and awake mode or between any other suitable modes. Input component 110 c mayinclude a two-position slider that may disable one or more outputcomponents 112 in certain modes of electronic device 100. Inputcomponents 110 d and 110 e may include buttons for increasing anddecreasing the volume output or any other characteristic output of anoutput component 112 of electronic device 100. Each one of inputcomponents 110 a-110 e may be a mechanical input component, such as abutton supported by a dome switch, a sliding switch, a control pad, akey, a knob, a scroll wheel, or any other suitable form.

An output component 112 a may be a display that can be used to display avisual or graphic user interface (“GUI”) 180, which may allow a user tointeract with electronic device 100. GUI 180 may include various layers,windows, screens, templates, elements, menus, and/or other components ofa currently running application (e.g., application 103 and/orapplication 143) that may be displayed in all or some of the areas ofdisplay output component 112 a. One or more of user input components 110a-110 i may be used to navigate through GUI 180. For example, one userinput component 110 may include a scroll wheel that may allow a user toselect one or more graphical elements 182 of GUI 180. Icons 182 may alsobe selected via a touch screen I/O component 114 a that may includedisplay output component 112 a and an associated touch input component110 f. Such a touch screen I/O component 114 a may employ any suitabletype of touch screen input technology, such as, but not limited to,resistive, capacitive, infrared, surface acoustic wave, electromagnetic,or near field imaging. Furthermore, touch screen I/O component 114 a mayemploy single point or multi-point (e.g., multi-touch) input sensing.

Icons 182 may represent various layers, windows, screens, templates,elements, and/or other components that may be displayed in some or allof the areas of display component 112 a upon selection by the user.Furthermore, selection of a specific icon 182 may lead to a hierarchicalnavigation process. For example, selection of a specific icon 182 maylead to a new screen of GUI 180 that may include one or more additionalicons or other GUI elements of the same application or of a newapplication associated with that icon 182. Textual indicators 181 may bedisplayed on or near each icon 182 to facilitate user interpretation ofeach graphical element icon 182. It is to be appreciated that GUI 180may include various components arranged in hierarchical and/ornon-hierarchical structures. When a specific icon 182 is selected,device 100 may be configured to open a new application associated withthat icon 182 and display a corresponding screen of GUI 180 associatedwith that application. For example, when the specific icon 182 labeledwith an NFC LOW POWER MODE textual indicator 181 (i.e., specific icon183) is selected, device 100 may launch or otherwise access a specificNFC low power mode or wallet mode application (e.g., application 143)and may display screens of a specific user interface that may includeone or more tools or features for interacting with NFC component 120 ina specific manner (see, e.g., FIGS. 4A-4G for specific examples of suchdisplays of GUI 180 during an NFC low power mode). For each application,screens may be displayed on display output component 112 a and mayinclude various user interface elements. Additionally or alternatively,for each application, various other types of non-visual information maybe provided to a user via various other output components 112 of device100.

Electronic device 100 also may include various other I/O components 114that may allow for communication between device 100 and other devices.I/O component 114 b may be a connection port that may be configured fortransmitting and receiving data files, such as media files or customerorder files, from a remote data source and/or power from an externalpower source. For example, I/O component 114 b may be a proprietaryport, such as a Lightning™ connector or a 30-pin dock connector fromApple Inc. of Cupertino, Calif. I/O component 114 c may be a connectionslot for receiving a SIM card or any other type of removable component.I/O component 114 d may be a headphone jack for connecting audioheadphones that may or may not include a microphone component.Electronic device 100 may also include at least one audio inputcomponent 110 g, such as a microphone, and at least one audio outputcomponent 112 b, such as an audio speaker.

Electronic device 100 may also include at least one tactile outputcomponent 112 c (e.g., a rumbler), a camera and/or scanner inputcomponent 110 h (e.g., a video or still camera, and/or a bar codescanner or any other suitable scanner that may obtain productidentifying information from a code, such as a bar code, a QR code, orthe like), and a biometric input component 110 i (e.g., a fingerprintreader or other feature recognition sensor, which may operate inconjunction with a feature-processing application that may be accessibleto electronic device 100 for authenticating a user). As shown in FIG. 2,at least a portion of biometric input component 110 i may beincorporated under or otherwise combined with input component 110 a orany other suitable I/O component of device 100. For example, biometricinput component 110 i may be a fingerprint reader that may be configuredto scan the fingerprint of a user's finger as the user interacts withmechanical input component 110 a by pressing input component 110 a withthat finger. As another example, biometric input component 110 i may bea fingerprint reader that may be combined with touch input component 110f of touch screen I/O component 114 a, such that biometric inputcomponent 110 i may be configured to scan the fingerprint of a user'sfinger as the user interacts with touch screen input component 110 f bypressing or sliding along touch screen input component 110 f with thatfinger. Moreover, as mentioned, electronic device 100 may furtherinclude NFC component 120, which may be communicatively accessible toterminal 10 via antenna 116 and/or antenna 134 (not shown in FIG. 2).NFC component 120 may be located at least partially within housing 101,and a mark or symbol 121 can be provided on the exterior of housing 101that may identify the general location of one or more of the antennasassociated with NFC component 120 (e.g., the general location of antenna116 and/or antenna 134).

To facilitate the following discussion regarding the operation ofelectronic device 100 in managing near field communications (e.g.,communications 55 with terminal 10) during an NFC low power mode ofoperation, reference is made to a schematic diagram of an NFC managementsubsystem 301 of electronic device 100 (e.g., as shown in FIG. 3) andfront views of screens 400 a-400 g that may be representative of agraphical user interface of electronic device 100 during such near fieldcommunication management (e.g., as shown in FIGS. 4A-4G). The operationdescribed may be achieved with a wide variety of graphical elements andvisual schemes. Therefore, the embodiments of FIGS. 4A-4G are notintended to be limited to the precise user interface conventions adoptedherein. Rather, embodiments may include a wide variety of user interfacestyles.

FIG. 3 shows a schematic view of near field communication managementsubsystem 301 of electronic device 100 that may be provided to managenear field communications during different modes of electronic device100. For example, NFC management subsystem 301 may determine when toutilize a low power NFC mode of electronic device 100 and/or how tomanage NFC component 120 during such a low power NFC mode (e.g., how tomake credentials of NFC component 120 appropriately secure and/orappropriately accessible during such a low power NFC mode).

Electronic device 100 can be configured to operate according todifferent power management modes for controlling and managing powerconsumption by the various components of device 100. As shown in FIG. 3,for example, NFC management subsystem 301 may include a mode detectionmodule 310 that may be configured to determine when to enter aparticular one of various power management modes of electronic device100. For example, mode detection module 310 may be configured todetermine when to enter a particular one of many possible powermanagement modes, such as a low power NFC mode of electronic device 100.In particular, mode detection module 310 can be configured to switch theoperation of electronic device 100 amongst various particular powermanagement modes for reducing power consumption when device 100 is notconnected to a remote power supply (e.g., when power supply 108 is notplugged into a wall socket). For example, operation of device 100 in aparticular power management mode can prevent non-essential powerintensive processes from being performed by device 100 while device 100is being powered by a battery that has less than a certain threshold ofpower potential remaining.

As shown in FIG. 3, mode detection module 310 may be configured to pollfor or otherwise receive power level data 307 from power supply 108,where power level data 307 may be indicative of the amount of powerremaining in power supply 108 (e.g., when power supply 108 may be abattery whose power level may diminish during use). When mode detectionmodule 310 detects that received power level data 307 of power supply108 has dropped below a particular threshold (e.g., below a 3.4 voltsvoltage threshold or any other suitable threshold), mode detectionmodule 310 may be configured to generate a switch command 311 that maybe configured to switch electronic device 100 to a low power NFC powermanagement mode (e.g., a “wallet” power management mode). For example,as shown in FIG. 3, when mode detection module 310 detects that receivedpower level data 307 is indicative of a particular characteristic ofpower supply 108 (e.g., that power supply 108 has dropped below aparticular power threshold), mode detection module 310 may be configuredto generate switch command 311 and provide switch command 311 to aswitch application module 320 of NFC management subsystem 301.

As another example of an initiation event of a low power NFC mode or awallet mode that may be detectable by mode detection module 310, modedetection module 310 may be configured to receive input mode selectiondata 309 from an input component 110 (e.g., one or more of inputcomponents 110 a-110 i). Such input mode selection data 309 may be anysuitable data generated by input component 110 that may be indicative ofa desire to enter such a wallet mode. For example, input mode selectiondata 309 may be indicative of a user selecting “NFC LOW POWER MODE” icon183 of GUI 180 using touch screen input component 110 f of I/O component114 a of FIG. 2, and this may be recognized by mode detection module 310as an initiation event for entering the wallet mode. Thus, when modedetection module 310 receives such specific input mode selection data309, mode detection module 310 may be configured to generate switchcommand 311 and provide switch command 311 to switch application module320 of NFC management subsystem 301. Therefore, in addition to or as analternative to device 100 switching to a wallet power management modewhen power supply 108 is below a certain power threshold, such a lowpower NFC power management mode may be entered at a user's discretion orduring any other suitable situation.

Regardless of why mode detection module 310 may generate switch command311 and transmit switch command 311 to switch application module 320(e.g., in response to a particular received power level data 307 and/orin response to a particular received input mode selection data 309),switch application module 320 may be configured to switch electronicdevice 100 into a low power NFC or wallet power management mode inresponse to receipt of such a switch command 311. This switch processcan include switch application module 320 generating and transmittingone or more disabling commands to one or more components of device 100for at least partially shutting down, removing power from, or otherwiseat least partially disabling at least one function of such components.This may reduce the power consumption of one or more components ofdevice 100 and/or may at least partially disable one, some, or allcomponents of device 100 that are not necessary for at least initiallyoperating device 100 in the wallet power management mode.

For example, in response to receipt of a switch command 311, switchapplication module 320 generate and transmit an NFC disabling command321 to NFC component 120 as part of the switching process to the walletpower management mode. NFC disabling command 321 may be configured to bereceived by any suitable element of NFC component 120 such that at leastone credential previously enabled by NFC component 120 prior to receiptof command 321 may be disabled in response to receipt of command 321. Asone particular example, command 321 may disable NFC antenna 134 and/orbooster 136 of NFC device module 130 when command 321 is received by NFCcomponent 120, such that no NFC communications 55 may be transmitted byNFC component 120 to terminal 10 after such disablement. As anotherexample, command 321 may disable a first applet 153 of a first SSD 154of NFC memory module 150 when command 321 is received by NFC component120, such that no NFC communications 55 associated with the credentialsof that first applet 153 may be transmitted by NFC component 120 toterminal 10 after such disablement. In some embodiments, command 321 maydisable every applet 153 of every SSD 154 of NFC memory module 150 whencommand 321 is received by NFC component 120, such that no NFCcommunications 55 associated with any credential of any applet 153 ofany SSD 154 may be transmitted by NFC component 120 to terminal 10 aftersuch disablement. However, in other embodiments, command 321 may disableonly some specific applets 153 of some SSDs 154 of NFC memory module 150when command 321 is received by NFC component 120, such that NFCcommunications 55 associated with the credentials of those specificapplets (e.g., credit card credentials, which may warrant a highsecurity level) may not be transmitted by NFC component 120 to terminal10 after such disablement, but such that other NFC communications 55that are associated with the credentials of other specific applets(e.g., simple transit system credentials, such as for the subway, whichmay not warrant a high security level) may be transmitted by NFCcomponent 120 to terminal 10 after such disablement. When received byNFC component 120, NFC disabling command 321 may be configured to shutdown, remove power from, or otherwise at least partially disable atleast one function of NFC component 120.

In addition to or as an alternative to generating NFC disabling command321, switch application module 320 may be configured to switchelectronic device 100 into a low power NFC or wallet power managementmode by generating and transmitting an output component disablingcommand 323 to at least one output component 112 (e.g., at least one ofoutput components 112 a-112 c). When received by that output component112, output component disabling command 323 may be configured to shutdown, remove power from, or otherwise at least partially disable atleast one function of that output component 112. For example, as shownin FIG. 4A, in response to display output component 112 a receiving sucha disabling command 323, display output component 112 a may beconfigured to provide a blank screen 400 a (e.g., display outputcomponent 112 a may be turned off) as opposed to screen 200 a of FIG. 2that may include various icons 182. Alternatively, as shown in screen400 a may include only a simple message or other element 401/402, whichmay indicate that device 100 is now in the wallet power management mode(e.g., display of simple element 401/402 of such a screen 400 a may bestatic and/or may only reside on a portion of display output component112 a, which may require less power than providing display of screen 200a). As another alternative, a simple icon 401 a, which may indicate to auser that device 100 is now in the wallet power management mode and notanother mode where certain other functions may be possible, may bedisplayed on screen 400 a (as well as all other screens 400 b-400 g ofFIGS. 4B-4G).

Similarly, switch application module 320 may be configured to switchelectronic device 100 into a low power NFC or wallet power managementmode by generating and transmitting an input component disabling command325 to at least one input component 110 (e.g., one or more of inputcomponents 110 a-110 i). When received by that input component 110,input component disabling command 325 may be configured to shut down,remove power from, or otherwise at least partially disable at least onefunction of that input component 110. Similarly, switch applicationmodule 320 may be configured to switch electronic device 100 into a lowpower NFC or wallet power management mode by generating and transmittingan application disabling command 327 to processor 102. When received byprocessor 102, application disabling command 327 may be configured toshut down or otherwise at least partially disable one or moreapplications currently being run by processor 102 (e.g., to force quitall non-native applications that were running on device 100 prior to thegeneration of that application disabling command 327). This may reducethe power consumption of processor 102 going forward with the switch tothe wallet mode. Moreover, additionally or alternatively, switchapplication module 320 may be configured to switch electronic device 100into a low power NFC or wallet power management mode by generating andtransmitting one or more additional disabling commands (not shown) to atleast one other component of device 100 (e.g., memory 104, communicationcomponent 106, antenna 116, etc.), such that, when received by thatdevice component, that component disabling command may be configured toshut down, remove power from, or otherwise at least partially disable atleast one function of that device component.

Therefore, switch application module 320 may be configured to initiatethe transition of electronic device 100 into a wallet power managementmode by generating and transmitting one or more disabling commands(e.g., disabling commands 321, 323, 325, 327, etc.) that may beconfigured to shut down, remove power from, or otherwise at leastpartially disable one, some, or all components of device 100 that arenot necessary for at least initially operating device 100 in the walletpower management mode. For example, as mentioned, one or more disablingcommands of switch application module 320 may be configured to at leastpartially turn off one or more input components 110, one or more outputcomponents 112, processor 102 or at least one or more applications beingrun by processor 102, at least some of memory 104, at least some or allof communications component 106, antenna 116, and/or some or all of NFCcomponent 120. When at least initially operating in such a wallet mode,electronic device 100 may be configured to refrain from providing powerto or otherwise enabling particular device components that are notnecessary for securely managing NFC component 120. For example, inresponse to receiving one or more disabling commands from switchapplication module 320, electronic device 100 can turn off a hard drive(e.g., memory 104), dim or turn off a display (e.g., output component112 a), place a processor (e.g., processor 102) in a low-power “sleep”or “hibernate” mode, and/or completely or partially disable NFCcomponent 120. Some or all of the power management settings of NFCmanagement subsystem 301 can be set automatically or by a user of device100 (e.g., the user may define a duration and/or a condition beforedevice 100 switches between particular power management modes and/or thecomponents that may be at least partially disabled or turned off whenswitching between different power management modes, such as the walletmode). By forcing electronic device 100 to operate in such a walletmode, switch application module 320 may eventually allow electronicdevice 100 to securely utilize NFC component 120 for communications 55in an efficient manner (e.g., until power supply 108 is no longer ableto power electronic device 100 to operate in that mode).

Therefore, at least certain modules of NFC management subsystem 301 maybe configured as a power management unit (“PMU”) that may be coupled toat least one source of power, such as power supply 108. Such a PMU mayinclude a microcontroller and can be configured to govern the powerfunctions of device 100. Such a PMU may include its own memory (e.g.,loaded with software and/or firmware), processor with input/outputfunctionality and timers, as well as one or more converters formeasuring the power provided by power supply 108. Moreover, additionallyor alternatively, such a PMU may include a backup power source that canpower components of NFC management subsystem 301 even when device 100 iscompletely shut down, such that, for example, the current time of areal-time clock may be maintained. Such a PMU may be responsible forcoordinating certain functions of device 100, including, but not limitedto, monitoring power connections and battery charges, controlling powerprovided to other components of device 100, shutting down certaincomponents of device 100 when they are left idle or deemed to becurrently unnecessary to properly operate device 100, regulating areal-time clock of device 100, and controlling various power managementmodes of device 100. A battery control circuit or power management stagemay be connected to a battery and to the base-band/firmware processor.One or more dedicated connections from such a PMU and/or from powersupply 108 to various elements of NFC component 120 (e.g., device module130, controller module 140, and/or memory module 150) may also beprovided by NFC management subsystem 301. These additional connectionsmay be provided to enable a battery control circuit or power supplycircuit to selectively power various components of device 100, andespecially the various components necessary to perform NFC communicationwith terminal 10.

When switch application module 320 has received switch command 311 frommode detection module 310 and has thereafter generated and transmittedone or more disabling commands (e.g., disabling commands 321, 323, 325,etc.) for at least partially disabling one, some, or all components ofdevice 100 that are not necessary for at least initially operatingdevice 100 in the wallet power management mode, switch applicationmodule 320 may also be configured to generate and transmit a launchingcommand 329 to an NFC low power mode control application module 330 ofNFC management subsystem 301. In response to receiving launching command329, control application module 330 may be configured to launch and runat least one application (e.g., application 143) that may bespecifically tailored to appropriately manage and/or otherwise controlelectronic device 100 in the low power NFC or wallet power managementmode. Therefore, operation of device 100 in such a low power NFC orwallet power management mode may be based on one or more applicationsaccessible to electronic device 100 (e.g., application 143) and/or basedon any input instructions being received by electronic device 100 (e.g.,via input component 110) that may control such an application.

When control application module 330 receives launching command 329 formanaging device 100 in the wallet power management mode, NFC component120 may be initially configured by NFC disabling command 321 to be in adisabled antenna mode (e.g., where antenna 116 and/or antenna 134 isunable to receive or transmit any NFC communications 55 (e.g., wherebooster 136 is disabled such that antenna 116 may not be able tocommunicate NFC communications 55)). Alternatively, when controlapplication module 330 receives launching command 329 for managingdevice 100 in the wallet power management mode, NFC component 120 may beinitially configured by NFC disabling command 321 to be in a passiveantenna mode (e.g., where antenna 116 and/or antenna 134 may bepassively enabled for NFC communication by terminal 10 when withinresponse range D of terminal 10). As yet another alternative, whencontrol application module 330 receives launching command 329 formanaging device 100 in the wallet power management mode, NFC component120 may be initially configured by NFC disabling command 321 to be in anactive antenna mode (e.g., where antenna 116 and/or antenna 134 may beactively enabled for NFC communication by electronic device 100 itself(e.g., by power supply 108)). It is to be understood that when NFCcomponent 120 is initially configured by NFC disabling command 321 to bein either the passive or active antenna modes, one or more otherelements of NFC component 120 (e.g., an applet 153 of one or more SSDs154) may be initially disabled by NFC disabling command 321 to prevent apassive/active antenna from communicating a credential of NFC component120 as communication 55 to terminal 10.

Continuing with the embodiments in which NFC component 120 may beinitially configured by NFC disabling command 321 to be in a disabledantenna mode, electronic device 100 may not be able to detect whendevice 100 is within an NFC response range D of terminal 10 (e.g., viaantenna 116 and/or via antenna 134) and may not be able to communicateNFC communication 55 with terminal 10. Instead, control applicationmodule 330 may be configured to wait for one or more input commands thatmay be indicative of a user's desire to interact with device 100 forpotentially enabling NFC component 120 for an NFC communication 55. Forexample, once initially switched to the wallet mode, device 100 mayprovide screen 400 a (e.g., a blank screen or turned off display 112 a)and may wait for a suitable UI unlock input command 331 a from anysuitable input component 110. Such a suitable unlock input command 331 amay be any input command that can be received by an input component 110for indicating a user's desire to interact with device 100 in the walletmode for potentially enabling at least a portion of NFC component 120.For example, UI unlock input command 331 a may be a simple userinteraction with home button input component 110 a. In such embodiments,all other input components 110 of device 100 may have been initiallydisabled by input component disabling command(s) 325, except for inputcomponent 110 a that may be frequently polled by control applicationmodule 330 for detecting such a UI unlock input command 331 a. This mayenable device 100 to use as little power as possible with respect to itsinput components 110 while still enabling a user interaction with device100 during the wallet mode that may indicate a user's potential desireto enable at least a portion of NFC component 120 for use during thewallet power management mode. It is to be understood that controlapplication module 330 may be configured to detect any suitable userinteraction via any suitable input component 110 or any suitablecombination of interactions via any suitable combination of inputcomponents 110 as an acceptable UI unlock input command 331 a. As shownin FIG. 4A, initial wallet mode screen 400 a may include a message 402that may prompt a user to provide a suitable UI unlock input command 331a for utilizing the wallet power management mode, where such message mayreassure the user that device 100 is in the wallet mode and notcompletely shut down. Alternatively, initial wallet mode screen 400 amay be blank and/or display output component 112 a may be completelyturned off.

Once an acceptable UI unlock input command 331 a has been received bycontrol application module 330, control application module 330 mayprovide a user with various options for utilizing device 100 in variousways while operating in the wallet power management mode. For example,as shown in FIG. 3, control application module 330 may generate andtransmit a confirm UI unlock command 333 a to at least one outputcomponent 112 of device 100 in response to receiving an acceptable UIunlock input command 331 a. Confirm UI unlock command 333 a may bereceived by an output component 112 and may configure that outputcomponent 112 to prompt a user to confirm his or her desire to interactwith device 100 to potentially utilize NFC component 120 (e.g., toconfirm acceptable UI unlock input command 331 a). For example, as shownin FIG. 4B, output display component 112 a may be configured to providescreen 400 b in response to receiving UI unlock command 333 a fromcontrol application module 330. Screen 400 b may prompt a user tointeract with device 100 in one or more ways to confirm that he or shewishes to potentially utilize NFC component 120. As shown, screen 400 bmay include a prompt 403 that may ask a user to slide an element along aparticular path of screen 400 b. Therefore, confirm UI unlock command333 a may also be received by input component 110 f of I/O component 114a for enabling such user interaction with input component 110 f of I/Ocomponent 114 a if input component 110 f had previously been disabled(e.g., by command 325). It is to be understood that confirm UI unlockcommand 333 a may be received by and may configure any suitablecombination of output components 112 other than display output component112 a to prompt a user to confirm his or her UI unlock command 331 a.For example, confirm UI unlock command 333 a may be received by and mayconfigure audio speaker output component 112 b to audibly ask a user toconfirm his or her UI unlock command 331 a.

In response to a confirm UI unlock command 333 a prompting a user via anoutput component 112 to confirm his or her UI unlock command 331 a, aninput component 110 may be configured to receive and transmit such aconfirmation as UI unlock confirmation data 331 b to control applicationmodule 330. For example, a user may slide the element along theparticular path of screen 400 b such that touch input component 110 f ofI/O component 114 a may transmit UI unlock confirmation data 331 b tocontrol application module 330. Any other suitable input component 110(e.g., microphone input component 110 g) may be configured to receiveand transmit a suitable UI unlock confirmation data 331 b to controlapplication module 330 (e.g., a user's voice command). Alternatively, ifno UI unlock confirmation data 331 b is received (e.g., after a certainduration of time since data 331 a is received), control applicationmodule 330 may once again return to screen 400 a (e.g., a state where auser must provide a new suitable UI unlock input command 331 a).

Once acceptable UI unlock confirmation data 331 b is received, controlapplication module 330 may be configured to provide a user with anability to authenticate his or her right to access NFC component 120 ofdevice 100. For example, as shown in FIG. 3, in response to receivingacceptable UI unlock confirmation data 331 b, control application module330 may generate and transmit an NFC component authentication requestcommand 333 b to at least one output component 112 of device 100. NFCcomponent authentication request command 333 b may be received by anoutput component 112 and may configure that output component 112 toprompt a user to provide device 100 with any suitable authenticationinformation that may prove the user's right to enable at least a portionof NFC component 120 in the wallet power management mode. For example,as shown in FIG. 4C, NFC component authentication request command 333 bmay be received by display output component 112 a and may configuredisplay output component 112 a to provide screen 400 c to the user.Screen 400 c may include turn off device option 405, exit wallet modeoption 407, cancel authentication option 409, and/or authenticationprompt 411. User selection of turn off device option 405 may causecontrol application module 330 to completely power down device 100(e.g., by transmitting a shutdown command 335 to power supply 108). Userselection of exit wallet mode option 407 may cause control applicationmodule 330 to return to a previous power management mode of device 100(e.g., by transmitting a wallet mode exit command 337 to switchapplication module 320). Whereas user selection of cancel authenticationoption 409 may cause control application module 330 to once againprovide screen 400 a and/or await another acceptable UI unlock inputcommand 331 a.

Authentication prompt 411 may include one or more suitable NFC componentauthentication options (e.g., one or more of NFC componentauthentication options 413 and 417) that a user may follow forattempting to authenticate himself or herself for general use of NFCcomponent 120. NFC component authentication option 413 may prompt a userto leverage a biometric sensor input component of device 100 (e.g.,sensor input component 110 i) for authenticating that the user has theright to access NFC component 120. For example, biometric sensor inputcomponent 110 i may include a fingerprint reader or other featurerecognition device and may operate in conjunction with afeature-processing program accessible to control application module 330(e.g., application 143). NFC component authentication option 417 mayprovide a virtual keypad or other data entry mechanism that may beutilized by the user to enter a personal identification number (“PIN”)or other suitable code for authenticating that the user has the right toaccess NFC component 120. Various other authentication options may beprovided by prompt 411, which itself may be provided by any suitableoutput component other than display output component 112 a (e.g., anauthentication prompt may be provided audibly to a user via audiospeaker output component 112 b, which may audibly ask the user toleverage a biometric sensor or enter a suitable code or password, whichmay enable display output component 112 a to be off).

A user may respond to authentication prompt 411 for NFC componentauthentication information by providing any suitable NFC component userauthentication data 331 c to control application module 330 via anysuitable input component 110 or any suitable combination of inputcomponents 110. For example, a user may respond to NFC componentauthentication option 413 by providing NFC component user authenticationdata 331 c to control application module 330 via user interaction withbiometric sensor input component 110 i (e.g., by swiping his or herfinger across a fingerprint scanner input of component 110 i). Asanother example, a user may respond to NFC component authenticationoption 417 by providing NFC component user authentication data 331 c tocontrol application module 330 via user interaction with touch inputcomponent 110 f of I/O component 114 a (e.g., by entering a PIN or othercode via the virtual keypad of FIG. 4C). It is to be understood that NFCcomponent user authentication data 331 c may be provided via anysuitable input component 110 or any suitable combination of inputcomponents 110 (e.g., NFC component user authentication data 331 c maybe provided by a user pressing one or more mechanical input components110 a-110 e in a specific order within a specific duration of time orspeaking a specific phrase into microphone input component 110 g, whichmay enable display output component 112 a to be off).

Control application module 330 may be configured to analyze any receivedNFC component user authentication data 331 c to determine whether theuser is indeed authorized to enable NFC component 120 for an NFCcommunication 55 while device 100 is in the wallet power managementmode. This may be done by comparing any received NFC component userauthentication data 331 c with a table of authentication informationassociated with NFC component 120. For example, received NFC componentuser authentication data 331 c may be compared to information associatedwith general authentication of ISD 152 of NFC component 120, as opposedto specific authentication of a specific applet 153 of a specific SSD154.

Once acceptable NFC component user authentication data 331 c isreceived, control application module 330 may be configured to determineif multiple credentials are available to NFC component 120 and, if so,provide a user with an ability to select from among the multiplecredentials that may be available to NFC component 120 for use duringthe wallet power management mode. For example, as shown in FIG. 1, NFCmemory module 150 may include a first SSD 154, a second SSD 154 a, and athird SSD 154 b, each of which may be associated with a differentcredential provisioned on NFC component 120. In such an embodiment, inresponse to receiving an acceptable NFC component user authenticationdata 331 c, control application module 330 may be configured to enable auser to select from among those three credentials of SSDs 154-154 b. Asshown in FIG. 3, in response to receiving acceptable NFC component userauthentication data 331 c, control application module 330 may generateand transmit an NFC credential selection request command 333 c to atleast one output component 112 of device 100. NFC credential selectionrequest command 333 c may be received by an output component 112 and mayconfigure that output component 112 to prompt a user to provide device100 with any suitable selection information that may indicate the user'sselection of a particular available credential for use by NFC component120 in the wallet power management mode. For example, as shown in FIG.4D, NFC credential selection request command 333 c may be received bydisplay output component 112 a and may configure display outputcomponent 112 a to provide screen 400 d to the user. Screen 400 d mayinclude first credential selection option 419, second credentialselection option 421, third credential selection option 423, and/orcancel credential selection option 425. User selection of cancelcredential selection option 425 may cause control application module 330to once again provide screen 400 c and/or await suitable NFC componentuser authentication data 331 c.

If a user wishes to select a particular available credential for use, heor she may select the appropriate option of provided credentialselection options 419, 421, and 423. Credential selection options 419,421, and 423 may prompt a user to leverage any suitable input component110 for selection of a particular credential option. For example, eachone provided credential selection options 419, 421, and 423 may providea virtual button or other data entry mechanism on I/O component 114 athat may be utilized by the user to select a particular credential.Credential selection options 419, 421, and 423 may be provided by anyother suitable output component other than display output component 112a of I/O component 114 a (e.g., a list of credential selection optionsmay be provided audibly to a user via audio speaker output component 12b, which may enable display output component 112 a to be off).

A user may respond to credential selection options 419, 421, and 423 byproviding any suitable credential selection response data 331 d tocontrol application module 330 via any suitable input component 110 orany suitable combination of input components 110. For example, a usermay respond to credential selection options 419, 421, and 423 byproviding credential selection response data 331 d to controlapplication module 330 via user interaction with touch input component110 f of I/O component 114 a (e.g., by selecting one of the virtualbuttons of FIG. 4D). It is to be understood that credential selectionresponse data 331 d may be provided via any suitable input component 110or any suitable combination of input components 110 (e.g., credentialselection response data 331 d may be provided by a user pressing aspecific one of mechanical input components 110 a-110 e that may beassociated with a specific credential selection option and/or by a userswiping a specific finger across biometric sensor input component 110 ithat may be associated with a specific credential selection option, eachof which may enable display output component 112 a to be off).

Control application module 330 may be configured to analyze any receivedcredential selection response data 331 d to determine which of theavailable credentials the user wishes to utilize for an NFCcommunication 55 while device 100 is in the wallet power managementmode. Once acceptable credential selection response data 331 d isreceived for a specific available credential, control application module330 may be configured to provide a user with an ability to authenticatehis or her right to access that selected credential. For example, asshown in FIG. 3, in response to receiving acceptable credentialselection response data 331 d, control application module 330 maygenerate and transmit an NFC credential authentication request command333 d to at least one output component 112 of device 100. NFC credentialauthentication request command 333 d may be received by any outputcomponent 112 and may configure that output component 112 to prompt auser to provide device 100 with any suitable authentication informationthat may prove the user's right to utilize the selected credential ofNFC component 120 in the wallet power management mode. For example, asshown in FIG. 4E. NFC credential authentication request command 333 dmay be received by display output component 112 a and may configuredisplay output component 112 a to provide screen 400 e to the user.Screen 400 e may include one or more suitable NFC credentialauthentication options (e.g., one or more of NFC credentialauthentication options 427 and 429) and/or cancel credentialauthentication option 431. User selection of cancel credentialauthentication option 431 may cause control application module 330 toonce again provide screen 400 d and/or await another acceptablecredential selection response data 331 d.

NFC credential authentication option 427 may prompt a user to leverage abiometric sensor input component of device 100 (e.g., sensor inputcomponent 110 i) for authenticating that the user has the right toaccess the selected credential of NFC component 120. For example,biometric sensor input component 110 i may include a fingerprint readeror other feature recognition device and may operate in conjunction witha feature-processing program accessible to control application module330 (e.g., application 103 and/or application 143). NFC credentialauthentication option 429 may provide a virtual keypad or other dataentry mechanism that may be utilized by the user to enter a personalidentification number (“PIN”) or other suitable code for authenticatingthat the user has the right to access the selected credential of NFCcomponent 120. Various other authentication options may be provided byNFC credential authentication options 427 and 429, which themselves maybe provided by any suitable output component other than display outputcomponent 112 a (e.g., an authentication prompt may be provided audiblyto a user via audio speaker output component 112 b, which may enabledisplay output component 112 a to be off).

A user may respond to NFC credential authentication options 427 and/or429 by providing any suitable NFC credential user authentication data331 e to control application module 330 via any suitable input component110 or any suitable combination of input components 110. For example, auser may respond to NFC credential authentication option 427 byproviding NFC component user authentication data 331 e to controlapplication module 330 via user interaction with biometric sensor inputcomponent 110 i (e.g., by swiping his or her finger across a fingerprintscanner input of component 110 i). As another example, a user mayrespond to NFC credential authentication option 429 by providing NFCcredential user authentication data 331 e to control application module330 via user interaction with touch input component 110 f of I/Ocomponent 114 a (e.g., by entering a PIN or other code via the virtualkeypad of FIG. 4E). It is to be understood that NFC credential userauthentication data 331 e may be provided via any suitable inputcomponent 110 or any suitable combination of input components 110 (e.g.,NFC credential user authentication data 331 e may be provided by a userpressing one or more mechanical input components 110 a-110 e in aspecific order within a specific duration of time, which may enabledisplay output component 112 a to be off).

Control application module 330 may be configured to analyze any receivedNFC credential user authentication data 331 e to determine whether theuser is indeed authorized to utilize the selected credential of NFCcomponent 120 for an NFC communication 55 while device 100 is in thewallet power management mode. This may be done by comparing any receivedNFC credential user authentication data 331 e with a table ofauthentication information associated with the selected credential ofNFC component 120. For example, received NFC credential userauthentication data 331 e may be compared to information associated withthe SSD 154 associated with the specifically selected credential.

Once acceptable NFC credential user authentication data 331 e isreceived, control application module 330 may be configured to enable NFCcomponent 120 to utilize the selected and authorized credential for NFCcommunication 55 with terminal 10. As shown in FIG. 3, in response toreceiving acceptable NFC credential user authentication data 331 e,control application module 330 may enable the selected and authorizedcredential of NFC component 120 for use by generating and transmittingan NFC enable command 339 to NFC component 120. For example, such an NFCenable command 339 may be received by NFC component 120 and may beconfigured to enable NFC component 120 in any suitable way for utilizingthe selected and authorized credential for NFC communication 55 withterminal 10 (e.g., by unlocking the appropriate applet 153, and/or byproviding the appropriate data from that applet into data module 132,and/or by enabling antenna 116 (e.g., by powering booster 136), and/orby enabling antenna 134 for enabling NFC component 120 to utilize theselected credential for use as NFC communication 55).

Moreover, as shown in FIG. 3, in response to receiving acceptable NFCcredential user authentication data 331 e, control application module330 may also generate and transmit NFC enabled data 333 e to at leastone output component 112 of device 100. NFC enabled data 333 e may bereceived by an output component 112 and may configure that outputcomponent 112 to indicate to a user that the selected credential hasbeen enabled for NFC communication 55 in the wallet power managementmode. For example, as shown in FIG. 4F, NFC enabled data 333 e may bereceived by display output component 112 a and may configure displayoutput component 112 a to provide screen 400 f to the user. Screen 400 fmay include credential enablement information 433 and/or a cancelcredential enablement option 437. User selection of cancel credentialenablement option 437 may cause control application module 330 to onceagain provide screen 400 d while also disabling the currently enabledcredential.

However, if a user does not choose to cancel the enabled credential viaoption 437, control application module 330 may allow the enabledcredential to be potentially utilized by NFC component 120 for at leasta certain duration of time (e.g., duration of time 435 as shown in FIG.4F). Such duration of time 435 may be based on preferences of a userand/or based on preferences of a manufacturer of device 100, which maybe defined or otherwise dictated by an application running on device 100(e.g., application 103 and/or application 143). For example, duration435 may vary based on a security level associated with the enabledcredential (e.g., a credit card credential of option 419 may warrant ahigh security level and may demand a shorter duration 435, while acoupon credential of option 421 may warrant a medium security level andmay demand a medium duration 435, and while a metro card credential ofoption 423 may warrant a low security level and may demand a longer orundefined duration 435). Such duration 435 may be clocked by controlapplication module 330 and may be continuously updated as part ofcredential enablement information 433 by NFC enabled data 333 e (e.g.,on screen 400 f) so as to indicate to the user for how much longer thecredential may be enabled for potential use as NFC communication 55before once again being disabled.

If, at any time during duration 435, the enabled credential is actuallyutilized by NFC component 120 as an NFC communication 55 (e.g., inresponse to terminal 10 receiving information associated with thatenabled credential), NFC component 120 may generate and transmit NFCstatus information 341 to control application module 330, as shown inFIG. 3. Moreover, in response to receipt of such NFC status information341, control application module 330 may generate and transmit NFC usedata 333 f to at least one output component 112 of device 100, as alsoshown in FIG. 3. NFC use data 333 f may be received by an outputcomponent 112 and may configure that output component 112 to indicate toa user that the enabled credential has been used for NFC communication55 in the wallet power management mode. For example, as shown in FIG.4G, NFC use data 333 f may be received by display output component 112 aand may configure display output component 112 a to provide screen 400 gto the user. Screen 400 g may include credential use information 439,which may include specific use explanation information 441. Such useinformation may be based on NFC use data 333 f, which may be determinedbased on NFC status information 341 provided by NFC component 120. Suchuse information 439/441 may be indicative of any suitablecharacteristics of the use of the enabled credential, such as the nameof the credential, the time of use, a description of terminal 10 thatparticipated in the use, and the like. Various other types of useinformation 439/441 may be defined by NFC use data 333 f and all suchuse information may be provided by any suitable output component otherthan display output component 112 a (e.g., use information may beprovided audibly to a user via audio speaker output component 112 b,which may enable display output component 112 a to be off).

Moreover, if the enabled credential is not actually utilized by NFCcomponent 120 as an NFC communication 55 during duration 435, NFCcomponent 120 may also generate and transmit NFC status information 341to control application module 330. In response to receipt of such NFCstatus information 341 indicative of non-use, control application module330 may generate and transmit NFC use data 333 f to at least one outputcomponent 112 of device 100, as also shown in FIG. 3. NFC use data 333 fmay be received by an output component 112 and may configure that outputcomponent 112 to indicate to a user that the enabled credential was notused for NFC communication 55 within the allowed duration 435. Forexample, as shown in FIG. 4G, NFC use data 333 f may be received bydisplay output component 112 a and may configure display outputcomponent 112 a to provide screen 400 g to the user. Screen 400 g mayinclude credential use information 439, which may include specificnon-use explanation information 441. Such non-use information may bebased on NFC use data 333 f, which may be determined based on NFC statusinformation 341 provided by NFC component 120. Such non-use information439/441 may be indicative of the non-use (e.g., the duration allowed,etc.). Various other types of non-use information 439/441 may be definedby NFC use data 333 f and all such non-use information may be providedby any suitable output component other than display output component 112a (e.g., non-use information may be provided audibly to a user via audiospeaker output component 112 b or haptically to a user via rumbleroutput component 112 c, which may enable display output component 112 ato be off).

After use or non-use of an enabled credential of NFC component 120 inthe wallet power management mode and after the provision of NFC use data333 f to at least one output component 112 of device 100, controlapplication module 330 may return electronic device 100 to its state atthe outset of the wallet power management mode (e.g., by providingscreen 400 a of FIG. 4A and operating device 100 in a state where a usermay provide a new suitable UI unlock input command 331 a).

NFC component 120 may only include a single credential. In suchinstances, once acceptable NFC component user authentication data 331 cis received by control application module 330 (e.g., as described withrespect to FIG. 4C), rather than providing a user with an ability toselect from among multiple credentials (e.g., as described with respectto FIGS. 4D and 4E), control application module 330 may be configured toimmediately enable NFC component 120 to utilize the single credentialfor NFC communication 55 with terminal 10 by generating and transmittingan NFC enable command 339 to NFC component 120 as well as by generatingand transmitting NFC enabled data 333 e to at least one output component112 of device 100 (e.g., as described with respect to FIG. 4F).

Moreover, in some embodiments, as mentioned above, NFC component 120 maybe initially configured by NFC disabling command 321 to be in either apassive or active antenna mode when device 100 is initially entered intothe wallet power management mode, such that an antenna of electronicdevice 100 may detect when device 100 is within an NFC response range Dof terminal 10. In such embodiments, in addition to or as an alternativeto waiting for a suitable UI unlock input command 331 a from anysuitable input component 110 (e.g., as described above with respect toFIG. 4A), control application module 330 may wait for suitable terminaldetect data 343 from NFC component 120. Such terminal detect data 343may be generated and transmitted by NFC component 120 to controlapplication module 330 whenever NFC component 120 is in either a passiveor active antenna mode during the wallet power management mode of device100 and whenever such an NFC component 120 also detects that device 100is within an NFC response range D of terminal 10. In such instances,control application module 330 may receive such terminal detect data 343and may then be configured to provide a user with an ability toauthenticate his or her right to enable NFC component 120 for conductingan NFC communication 55 with the detected terminal 10. For example, asshown in FIG. 3, in response to receiving terminal detect data 343,control application module 330 may generate and transmit NFC componentauthentication request command 333 b to at least one output component112 of device 100 (e.g., as described above with respect to FIG. 4C) forprompting a user to provide device 100 with any suitable authenticationinformation that may prove the user's right to enable at least a portionof NFC component 120 in the wallet power management mode. Therefore, insome embodiments of wallet mode operation, a user may be prompted forauthentication in response to NFC component 120 detecting a terminal 10.Whereas, in some other embodiments of wallet mode operation, NFCcomponent 120 may not be enabled to detect a terminal 10 until after auser has been authenticated to use NFC component 120. Thus, controlapplication module 330 may prompt a user for authentication of NFCcomponent 120 in response to at least two different types of anauthentication initiation event (e.g., either in response to receiving asuitable UI unlock input command 331 a or in response to receivingsuitable terminal detect data 343).

FIG. 5 is a flowchart of an illustrative process 500 for managing nearfield communications. At step 502 of process 500, an initiation eventfor a low power NFC or “wallet” power management mode may be detected.For example, as described with respect to FIG. 3, mode detection module310 may be configured to detect such an initiation event based onreceived power level data 307 from power supply 108 and/or based onreceived input mode selection data 309 from input component 110. Process500 may continuously repeat step 502 until an initiation event isdetected.

Next, once such an initiation event is detected at step 502, process 500may proceed to switch an electronic device to a wallet mode. This switchmay include at least one of steps 504, 506, and/or 508. For example,process 500 may proceed from step 502 to step 504 and shut down at leastone application that had been running. As described with respect to FIG.3, switch application module 320 may generate and transmit anapplication disabling command 327 to processor 102 of electronic device100 for shutting down one or more applications. Step 504 mayadditionally or alternatively include at least partially shutting down,removing power from, or otherwise at least partially disabling at leastone function of any I/O component of the device (e.g., input component110 and/or output component 112 of device 100).

Process 500 may then proceed from step 504 to step 506 and disable atleast a portion of an NFC component. For example, as described withrespect to FIG. 3, switch application module 320 may generate andtransmit an NFC disabling command 321 to NFC component 120 for disablingone or more credentials of one or more SSDs 154, disabling antenna 134or booster 136 of device module 130, or for disabling any other suitableelement of NFC component 120 that may prevent at least one credential ofNFC component 120 from being communicated as NFC communication 55 toterminal 10. Such disabling may reduce the power consumption of NFCcomponent 120 and/or may prevent NFC component 120 from functioning in apassive state. Additionally or alternatively, the switching of anelectronic device to a wallet mode of process 500 may include step 508,where an application for managing the device in the wallet mode may belaunched and run by the device. For example, as described with respectto FIG. 3, switch application module 320 may generate and transmitlaunching command 329 to control application module 330 for launchingand running at least one application (e.g., application 143) that may bespecifically tailored to appropriately manage and/or otherwise controlelectronic device 100 in the low power NFC or wallet power managementmode.

Next, once the electronic device is operating in the wallet low powermode, process 500 may proceed to step 510 for detecting a UI unlockinput command. For example, as described with respect to FIG. 3, controlapplication module 330 may be configured to wait for one or moresuitable UI unlock input commands 331 a from an input component 110 thatmay be indicative of a user's desire to interact with device 100 forpotentially utilizing NFC component 120 for an NFC communication 55 inthe wallet mode. If such a command is detected at step 510, process 500may proceed to step 512 for confirming a user's desire to interact withdevice 100. For example, as described with respect to FIG. 3 and FIG.4B, control application module 330 may generate and transmit a confirmUI unlock command 333 a to at least one output component 112 to prompt auser to confirm his or her desire to interact with device 100 in thewallet mode. If such a desire is confirmed at step 512 (e.g., by controlapplication module 330 receiving UI unlock confirmation data 331 b),process 500 may proceed to step 514 for determining whether the userwishes to turn off the device, which he or she may do by proceeding tostep 516 and ending process 500 by shutting down the device. However, ifthe user does not wish to shut down the device at step 514, process 500may proceed to step 518 for determining whether the user wishes tocancel the unlock and quit interacting with the device, which he or shemay do by having process 500 return to step 510. However, if the userdoes not wish to quit interacting with the device at step 518, process500 may proceed to step 520 for determining whether the user wishes toexit the wallet mode, which he or she may do by having process 500 quitthe mode at step 521 and return to step 502. However, if the user doesnot wish to exit the wallet mode at step 520, process 500 may proceed tostep 522 for attempting to authenticate the user for enabling the NFCcomponent. For example, each one of steps 512-522 may be described withrespect to FIGS. 3 and 4C.

At step 522, process 500 may prompt a user to authenticate himself orherself for use of the NFC component. For example, as described withrespect to FIGS. 3 and 4C, control application module 330 may generateand transmit an NFC component authentication request command 333 b to atleast one output component 112 of device 100. If the user issuccessfully able to be authenticated for use of the NFC component(e.g., by providing NFC component user authentication data 331 c tocontrol application module 330 via user interaction with an inputcomponent 110), process 500 may proceed to step 524, otherwise process500 may return to step 510.

In some embodiments, a user may be authenticated by the same userinteraction with device 100 that may generate a UI unlock input command331 a detected at step 510 such that process 500 may combine steps 510and 522. For example, as described above with respect to FIG. 2, abiometric input component (e.g., biometric input component 110 i) may beincorporated in another input component (e.g., home button inputcomponent 110 a), and, as described with respect to FIGS. 3 and 4A, a UIunlock input command 331 a may be a simple user interaction with homebutton input component 110 a. Accordingly, such a user interaction withhome button input component 110 a for generating a UI unlock inputcommand 331 a may also be a user interaction with biometric sensor inputcomponent 110 i for providing NFC component user authentication data 331c to control application module 330. In such instances, process 500 mayjump from step 510 to step 524 (e.g., bypassing one or more of steps512-522), as authentication step 522 may be unnecessary due to the NFCcomponent user authentication data 331 c detected at step 510 along withUI unlock input command 331 a.

Additionally or alternatively, a user may be authenticated by the sameuser interaction with device 100 that may generate UI unlockconfirmation data 331 b detected at step 512 such that process 500 maycombine steps 512 and 522. For example, as described above with respectto FIG. 2, a biometric input component (e.g., biometric input component110 i) may be incorporated in another I/O component of device 100 (e.g.,touch input component 110 f of I/O component 114 a), and, as describedwith respect to FIGS. 3 and 4B, UI unlock confirmation data 331 b may bea simple user interaction with touch input component 110 f of I/Ocomponent 114 a for sliding an element along a particular path of screen400 b. Accordingly, such a user interaction with touch input component110 f of I/O component 114 a for generating UI unlock confirmation data331 b may also be a user interaction with biometric sensor inputcomponent 110 i for providing NFC component user authentication data 331c to control application module 330. In such instances, process 500 mayjump from step 512 to step 524 (e.g., bypassing one or more of steps512-522), as authentication step 522 may be unnecessary due to the NFCcomponent user authentication data 331 c detected at step 512 along withUI unlock confirmation data 331 b.

At step 524, process 500 may determine if more than one credential maybe accessible to the NFC component authenticated by the user. If so,process 500 proceeds to step 526, otherwise process 500 may proceed tostep 530. At step 526, process 500 may prompt a user to select amongstmultiple credentials available to the NFC Component (e.g., controlapplication module 330 may generate and transmit an NFC credentialselection request command 333 c to at least one output component 112 ofdevice 100). If the user successfully selects one of the multiplecredentials at step 526 (e.g., by providing any suitable credentialselection response data 331 d to control application module 330 via anysuitable input component 110), process 500 may proceed to step 528,otherwise process 500 may return to step 522.

At step 528, process 500 may prompt a user to authenticate himself orherself for use of the selected credential. For example, as describedwith respect to FIGS. 3 and 4E, control application module 330 maygenerate and transmit an NFC credential authentication request command333 d to at least one output component 112 of device 100. If the user issuccessfully able to be authenticated for use of the selected credential(e.g., by providing NFC credential user authentication data 331 e tocontrol application module 330 via user interaction with an inputcomponent 110), process 500 may proceed to step 530, otherwise process500 may return to step 526.

At step 530, process 500 may enable the authorized credential of the NFCcomponent and determine whether a duration of the authorization hasexpired. For example, as described with respect to FIG. 3, controlapplication module 330 may enable the selected and authorized credentialof NFC component 120 for use by generating and transmitting an NFCenable command 339 to NFC component 120 to enable NFC component 120 inany suitable way for utilizing the selected and authorized credentialfor NFC communication 55 with terminal 10, where control applicationmodule 330 may allow the enabled credential to be potentially utilizedby NFC component 120 for at least a certain duration of time 435. If theauthorization has expired, process 500 may proceed from step 530 to step534, otherwise process 500 may proceed from step 530 to step 532.

At step 532, process 500 may determine whether the authorized credentialhas been used in an NFC transaction. If the credential has been used inan NFC transaction, process 500 may proceed from step 532 to step 534,otherwise process 500 may return from step 532 to step 530 fordetermining whether the duration has expired. At step 534, process 500may provide a description of the use or non-use of the authorizedcredential and may then return to step 510. For example, as describedwith respect to FIGS. 3 and 4G, if, at any time during duration 435, theenabled credential is actually utilized by NFC component 120 as an NFCcommunication 55 (e.g., in response to terminal 10 receiving informationassociated with that enabled credential), NFC component 120 may generateand transmit NFC status information 341 to control application module330, and, in response to receipt of such NFC status information 341,control application module 330 may generate and transmit NFC use data333 f to at least one output component 112 of device 100. Moreover, asdescribed with respect to FIGS. 3 and 4G, if the enabled credential isnot actually utilized by NFC component 120 as an NFC communication 55during duration 435, NFC component 120 may also generate and transmitNFC status information 341 to control application module 330, and, inresponse to receipt of such NFC status information 341 indicative ofnon-use, control application module 330 may generate and transmit NFCuse data 333 f to at least one output component 112 of device 100.

Returning to step 510, if no UI unlock input command is detected,process 500 may proceed from step 510 to step 536. At step 536, process500 may attempt to detect an NFC terminal. For example, as describedwith respect to FIG. 3, control application module 330 may wait forsuitable terminal detect data 343 from NFC component 120 that may begenerated and transmitted by NFC component 120 to control applicationmodule 330 whenever NFC component 120 is in either a passive or activeantenna mode during the wallet power management mode of device 100 andwhenever such an NFC component 120 detects that device 100 is within anNFC response range D of terminal 10. If such a terminal is detected,process 500 may proceed from step 536 to step 522, otherwise process 500may proceed from step 536 to step 510.

It is understood that the steps shown in process 500 of FIG. 5 aremerely illustrative and that existing steps may be modified or omitted,additional steps may be added, and the order of certain steps may bealtered.

FIG. 6 is a flowchart of an illustrative process 600 for managing nearfield communications on an electronic device. At step 602, process 600may receive authentication information using an input component of theelectronic device. For example, as described with respect to FIG. 3,control application module 330 may generate and transmit an NFCcomponent authentication request command 333 b to at least one outputcomponent 112 of device 100, in response to which a user may beauthenticated for use of the NFC component (e.g., by providing NFCcomponent user authentication data 331 c to control application module330 via user interaction with an input component 110). Next, at step604, process 600 may power at least a first portion of a near fieldcommunication component of the electronic device based on theauthentication information received at step 602. For example, asdescribed with respect to FIG. 3, once suitable NFC component userauthentication data 331 c is received, control application module 330may enable NFC component 120 for use by generating and transmitting anNFC enable command 339 to NFC component 120. Such an NFC enable command339 may be configured to enable NFC component 120 by powering booster136, which may thereby enable antenna 116 for communicating NFCcommunications 55 with terminal 10.

It is understood that the steps shown in process 600 of FIG. 6 aremerely illustrative and that existing steps may be modified or omitted,additional steps may be added, and the order of certain steps may bealtered.

FIG. 7 is a flowchart of an illustrative process 700 for managing nearfield communications on an electronic device. At step 702, process 700may detect a low power mode initiation event. For example, as describedwith respect to FIG. 3, mode detection module 310 may be configured todetect such a low power mode initiation event based on received powerlevel data 307 from power supply 108 and/or based on received input modeselection data 309 from input component 110. Next, at step 704, process700 may disable an active element of the electronic device, such as anysuitable portion or function of any suitable component of device 100.For example, as described with respect to FIG. 3, switch applicationmodule 320 may generate and transmit an NFC disabling command 321 to NFCcomponent 120 for disabling one or more credentials of one or more SSDs154, disabling antenna 134 and/or booster 136 of device module 130,and/or for disabling any other suitable element of NFC component 120that may prevent at least one credential of NFC component 120 from beingcommunicated as NFC communication 55 to terminal 10. Such disabling mayreduce the power consumption of NFC component 120 and/or may prevent NFCcomponent 120 from functioning in a passive state. As another example,as also described with respect to FIG. 3, switch application module 320may generate and transmit an output component disabling command 323 toat least one output component 112 (e.g., at least one of outputcomponents 112 a-112 c) for shutting down, removing power from, orotherwise at least partially disabling at least one function of thatoutput component 112. As yet another example, as also described withrespect to FIG. 3, switch application module 320 may generate andtransmit an input component disabling command 325 to at least one inputcomponent 110 (e.g., at least one of input components 110 a-110 i) forshutting down, removing power from, or otherwise at least partiallydisabling at least one function of that input component 110. As yetanother example, as also described with respect to FIG. 3, switchapplication module 320 may generate and transmit one or more additionaldisabling commands (not shown) to at least one other component of device100 (e.g., memory 104, communication component 106, antenna 116, etc.),such that, when received by that device component, that componentdisabling command may be configured to shut down, remove power from, orotherwise at least partially disable at least one function of thatdevice component.

Next, at step 706, process 700 may close at least one active applicationthat was running on the electronic device prior to the detecting of step702. For example, as described with respect to FIG. 3, switchapplication module 320 may generate and transmit an applicationdisabling command 327 to processor 102 of electronic device 100 forshutting down one or more applications (e.g., force quitting allnon-native applications).

Next, at step 708, process 700 may run a low power mode application onthe electronic device, where the running of the low power modeapplication may include receiving authentication information from aninput component of the electronic device and enabling a near fieldcommunication component based on the received authenticationinformation. For example, as described with respect to FIG. 3, switchapplication module 320 may generate and transmit launching command 329to control application module 330 for launching and running at least oneapplication (e.g., application 143) that may be specifically tailored toappropriately manage and/or otherwise control electronic device 100 inthe low power NFC or wallet power management mode. While running thisapplication, control application module 330 may generate and transmit anNFC component authentication request command 333 b to at least oneoutput component 112 of device 100, in response to which a user may beauthenticated for use of the NFC component (e.g., by providing NFCcomponent user authentication data 331 c to control application module330 via user interaction with an input component 110). Once suitable NFCcomponent user authentication data is received, control applicationmodule 330 may enable NFC component 120 for use by generating andtransmitting an NFC enable command 339 to NFC component 120.

It is understood that the steps shown in process 700 of FIG. 7 aremerely illustrative and that existing steps may be modified or omitted,additional steps may be added, and the order of certain steps may bealtered.

FIG. 8 is a flowchart of an illustrative process 800 for managing nearfield communications on an electronic device. At step 802, process 800may detect a low power mode initiation event. For example, as describedwith respect to FIG. 3, mode detection module 310 may be configured todetect such a low power mode initiation event based on received powerlevel data 307 from power supply 108 and/or based on received input modeselection data 309 from input component 110. Next, at step 804, process800 may disable an element of the electronic device, such as anysuitable portion or function of any suitable component of device 100.For example, as described with respect to FIG. 3, switch applicationmodule 320 may generate and transmit an NFC disabling command 321 to NFCcomponent 120 for disabling one or more credentials of one or more SSDs154, disabling antenna 134 and/or booster 136 of device module 130,and/or for disabling any other suitable element of NFC component 120that may prevent at least one credential of NFC component 120 from beingcommunicated as NFC communication 55 to terminal 10. Such disabling mayreduce the power consumption of NFC component 120 and/or may prevent NFCcomponent 120 from functioning in a passive state. As another example,as also described with respect to FIG. 3, switch application module 320may generate and transmit an output component disabling command 323 toat least one output component 112 (e.g., at least one of outputcomponents 112 a-112 c) for shutting down, removing power from, orotherwise at least partially disabling at least one function of thatoutput component 112. As yet another example, as also described withrespect to FIG. 3, switch application module 320 may generate andtransmit an input component disabling command 325 to at least one inputcomponent 110 (e.g., at least one of output components 110 a-110 i) forshutting down, removing power from, or otherwise at least partiallydisabling at least one function of that input component 110. As yetanother example, as also described with respect to FIG. 3, switchapplication module 320 may generate and transmit one or more additionaldisabling commands (not shown) to at least one other component of device100 (e.g., memory 104, communication component 106, antenna 116, etc.),such that, when received by that device component, that componentdisabling command may be configured to shut down, remove power from, orotherwise at least partially disable at least one function of thatdevice component.

Next, at step 806, process 800 may identify an authentication initiationevent. Then, at step 808, in response to the identification of step 806,process 800 may provide on an output component of the electronic devicean output that requests user interaction for the enablement of a nearfield communication component. For example, as described with respect toFIG. 3, control application module 330 may prompt a user forauthentication of NFC component 120 in response to at least twodifferent types of an authentication initiation event (e.g., either inresponse to receiving a suitable UI unlock input command 331 a or inresponse to receiving suitable terminal detect data 343).

It is understood that the steps shown in process 800 of FIG. 8 aremerely illustrative and that existing steps may be modified or omitted,additional steps may be added, and the order of certain steps may bealtered.

Moreover, one, some, or all of the processes described with respect toFIGS. 1-8 may each be implemented by software, but may also beimplemented in hardware, firmware, or any combination of software,hardware, and firmware. Instructions for performing these processes mayalso be embodied as machine- or computer-readable code recorded on amachine- or computer-readable medium. In some embodiments, thecomputer-readable medium may be a non-transitory computer-readablemedium. Examples of such a non-transitory computer-readable mediuminclude but are not limited to a read-only memory, a random-accessmemory, a flash memory, a CD-ROM, a DVD, a magnetic tape, a removablememory card, and a data storage device (e.g., an optical data storagedevice, such as memory 104 and/or memory module 150 of FIG. 1). In otherembodiments, the computer-readable medium may be a transitorycomputer-readable medium. In such embodiments, the transitorycomputer-readable medium can be distributed over network-coupledcomputer systems so that the computer-readable code is stored andexecuted in a distributed fashion. For example, such a transitorycomputer-readable medium may be communicated from one electronic deviceto another electronic device using any suitable communications protocol(e.g., the computer-readable medium may be communicated to electronicdevice 100 via communications component 106 (e.g., as at least a portionof application 103 and/or application 143)). Such a transitorycomputer-readable medium may embody computer-readable code,instructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. A modulateddata signal may be a signal that has one or more of its characteristicsset or changed in such a manner as to encode information in the signal.

It is to be understood that any or each module of either one or both ofNFC component 120 and NFC management subsystem 301 may be provided as asoftware construct, firmware construct, one or more hardware components,or a combination thereof. For example, any or each module of either oneor both of NFC component 120 and NFC management subsystem 301 may bedescribed in the general context of computer-executable instructions,such as program modules, that may be executed by one or more computersor other devices. Generally, a program module may include one or moreroutines, programs, objects, components, and/or data structures that mayperform one or more particular tasks or that may implement one or moreparticular abstract data types. It is also to be understood that thenumber, configuration, functionality, and interconnection of the modulesof either one or both of NFC component 120 and NFC management subsystem301 are merely illustrative, and that the number, configuration,functionality, and interconnection of existing modules may be modifiedor omitted, additional modules may be added, and the interconnection ofcertain modules may be altered.

As described above, various disabling commands may be configured to shutdown, remove power from, or otherwise at least partially disable atleast one function of various components of device 100. For example,input component disabling command 325 may be configured to shut down,remove power from, or otherwise at least partially disable at least onefunction of an input component 110, and application disabling command327 may be configured to shut down, remove power from, or otherwise atleast partially disable one or more applications currently being run byprocessor 102 (e.g., to force quit all non-native applications that wererunning on device 100 prior to the generation of that applicationdisabling command 327), while NFC disabling command 321 may beconfigured to shut down, remove power from, or otherwise at leastpartially disable at least one function of NFC component 120. Similarly,various enabling commands may be configured to turn on, provide powerto, or otherwise at least partially enable at least one function ofvarious components of device 100. For example, NFC enable command 339may be configured to turn on, provide power to, or otherwise at leastpartially enable at least one function of NFC component 120. Suchcommands may enable or disable one or more various elements (e.g.,software constructs, firmware constructs, one or more hardwarecomponents, or a combination thereof) of a component of device 100 inone or more suitable ways for enabling or disabling at least onefunction of that component. For example, a software application runningon processor 102 may be disabled by unloading that application fromprocessor 102 and/or by turning off processor 102 altogether. As anotherexample, an otherwise powered up NFC component 120 with at least onecredential activated for use may be finally enabled for communicatingNFC communications 55 by providing suitable power to booster 136, suchthat shared antenna 116 may be properly used to transmit such NFCcommunications 55. As yet another example, an otherwise powered up NFCcomponent 120 with an antenna ready for transmitting NFC communications55 may be finally enabled for communicating NFC communications 55 byenabling at least one credential of NFC component 120 for use in suchcommunications 55. Enablement of at least one credential (e.g.,activation of an applet 153) may be accomplished by powering up orotherwise turning on the memory element on which that credential isstored and/or by transmitting a key or other security data to the SSD ofthat credential in order to decrypt the information of that credentialfor use by NFC component 120 as NFC communications 55.

At least a portion of one or more of the modules of either one or bothof NFC component 120 and NFC management subsystem 301 may be stored inor otherwise accessible to device 100 in any suitable manner (e.g., inmemory 104 of device 100 (e.g., as at least a portion of application 103and/or application 143)). Any or each module of either one or both ofNFC component 120 and NFC management subsystem 301 may be implementedusing any suitable technologies (e.g., as one or more integrated circuitdevices), and different modules may or may not be identical instructure, capabilities, and operation. Any or all of the modules orother components of either one or both of NFC component 120 and NFCmanagement subsystem 301 may be mounted on an expansion card, mounteddirectly on a system motherboard, or integrated into a system chipsetcomponent (e.g., into a “north bridge” chip).

Any or each module of either one or both of NFC component 120 and NFCmanagement subsystem 301 may be a dedicated system implemented using oneor more expansion cards adapted for various bus standards. For example,all of the modules may be mounted on different interconnected expansioncards or all of the modules may be mounted on one expansion card. Withrespect to NFC component 120, by way of example only, the modules of NFCcomponent 120 may interface with a motherboard or processor 102 ofdevice 100 through an expansion slot (e.g., a peripheral componentinterconnect (“PCI”) slot or a PCI express slot). Alternatively, NFCcomponent 120 need not be removable but may include one or morededicated modules that may include memory (e.g., RAM) dedicated to theutilization of the module. In other embodiments, NFC component 120 maybe integrated into device 100. For example, a module of NFC component120 may utilize a portion of device memory 104 of device 100. Any oreach module of either one or both of NFC component 120 and NFCmanagement subsystem 301 may include its own processing circuitry and/ormemory. Alternatively, any or each module of either one or both of NFCcomponent 120 and NFC management subsystem 301 may share processingcircuitry and/or memory with any other module of NFC component 120and/or NFC management subsystem 301 and/or processor 102 and/or memory104 of device 100.

As mentioned, an input component 110 of device 100 (e.g., inputcomponent 110 f) may include a touch input component that can receivetouch input for interacting with other components of device 100 viawired or wireless bus 118. Such a touch input component 110 may be usedto provide user input to device 100 in lieu of or in combination withother input components, such as a keyboard, mouse, and the like.

A touch input component 110 may include a touch sensitive panel, whichmay be wholly or partially transparent, semitransparent,non-transparent, opaque, or any combination thereof. A touch inputcomponent 110 may be embodied as a touch screen, touch pad, a touchscreen functioning as a touch pad (e.g., a touch screen replacing thetouchpad of a laptop), a touch screen or touch pad combined orincorporated with any other input device (e.g., a touch screen or touchpad disposed on a keyboard), or any multi-dimensional object having atouch sensitive surface for receiving touch input. In some embodiments,the terms touch screen and touch pad may be used interchangeably.

In some embodiments, a touch input component 110 embodied as a touchscreen may include a transparent and/or semitransparent touch sensitivepanel partially or wholly positioned over, under, and/or within at leasta portion of a display (e.g., display output component 112 a). In otherembodiments, a touch input component 110 may be embodied as anintegrated touch screen where touch sensitive components/devices areintegral with display components/devices. In still other embodiments, atouch input component 110 may be used as a supplemental or additionaldisplay screen for displaying supplemental or the same graphical data asa primary display and to receive touch input.

A touch input component 110 may be configured to detect the location ofone or more touches or near touches based on capacitive, resistive,optical, acoustic, inductive, mechanical, chemical measurements, or anyphenomena that can be measured with respect to the occurrences of theone or more touches or near touches in proximity to input component 110.Software, hardware, firmware, or any combination thereof may be used toprocess the measurements of the detected touches to identify and trackone or more gestures. A gesture may correspond to stationary ornon-stationary, single or multiple, touches or near touches on a touchinput component 110. A gesture may be performed by moving one or morefingers or other objects in a particular manner on touch input component110, such as by tapping, pressing, rocking, scrubbing, rotating,twisting, changing orientation, pressing with varying pressure, and thelike at essentially the same time, contiguously, or consecutively. Agesture may be characterized by, but is not limited to, a pinching,pulling, sliding, swiping, rotating, flexing, dragging, or tappingmotion between or with any other finger or fingers. A single gesture maybe performed with one or more hands, by one or more users, or anycombination thereof.

As mentioned, electronic device 100 may drive a display (e.g., displayoutput component 112 a) with graphical data to display a graphical userinterface (“GUI”) 180. GUI 180 may be configured to receive touch inputvia a touch input component 110 f. Embodied as a touch screen (e.g.,with display output component 112 a as I/O component 114 a), touch I/Ocomponent 110 f may display GUI 180. Alternatively, GUI 180 may bedisplayed on a display (e.g., display output component 112 a) separatefrom touch input component 110 f. GUI 180 may include graphical elementsdisplayed at particular locations within the interface. Graphicalelements may include, but are not limited to, a variety of displayedvirtual input devices, including virtual scroll wheels, a virtualkeyboard, virtual knobs, virtual buttons, any virtual user interface(“UI”), and the like. A user may perform gestures at one or moreparticular locations on touch input component 110 f, which may beassociated with the graphical elements of GUI 180. In other embodiments,the user may perform gestures at one or more locations that areindependent of the locations of graphical elements of GUI 180. Gesturesperformed on a touch input component 110 may directly or indirectlymanipulate, control, modify, move, actuate, initiate, or generallyaffect graphical elements, such as cursors, icons, media files, lists,text, all or portions of images, or the like within the GUI. Forinstance, in the case of a touch screen, a user may directly interactwith a graphical element by performing a gesture over the graphicalelement on the touch screen. Alternatively, a touch pad may generallyprovide indirect interaction. Gestures may also affect non-displayed GUIelements (e.g., causing user interfaces to appear) or may affect otheractions of device 100 (e.g., affect a state or mode of a GUI,application, or operating system). Gestures may or may not be performedon a touch input component 110 in conjunction with a displayed cursor.For instance, in the case in which gestures are performed on a touchpad,a cursor or pointer may be displayed on a display screen or touch screenand the cursor or pointer may be controlled via touch input on thetouchpad to interact with graphical objects on the display screen. Inother embodiments, in which gestures are performed directly on a touchscreen, a user may interact directly with objects on the touch screen,with or without a cursor or pointer being displayed on the touch screen.Feedback may be provided to the user via bus 118 in response to or basedon the touch or near touches on a touch input component 110. Feedbackmay be transmitted optically, mechanically, electrically, olfactory,acoustically, or the like or any combination thereof and in a variableor non-variable manner.

While there have been described systems, methods, and computer-readablemedia for managing near field communications, it is to be understoodthat many changes may be made therein without departing from the spiritand scope of the subject matter described herein in any way.Insubstantial changes from the claimed subject matter as viewed by aperson with ordinary skill in the art, now known or later devised, areexpressly contemplated as being equivalently within the scope of theclaims. Therefore, obvious substitutions now or later known to one withordinary skill in the art are defined to be within the scope of thedefined elements.

Therefore, those skilled in the art will appreciate that the inventioncan be practiced by other than the described embodiments, which arepresented for purposes of illustration rather than of limitation.

What is claimed is:
 1. A method of operating an electronic devicecomprising: detecting a low power mode initiation event; in response tothe detection of the low power mode initiation event, disabling an inputcomponent of the electronic device; while the input component isdisabled, identifying an authentication initiation event with theelectronic device, wherein the identifying the authentication initiationevent comprises detecting a near field communication terminal with theelectronic device; and in response to the identification of theauthentication initiation event, re-enabling the input component of theelectronic device.
 2. The method of claim 1, wherein the input componentcomprises a touch sensitive surface operative to receive touch input. 3.The method of claim 1, wherein the identifying the authenticationinitiation event comprises receiving a user input with another inputcomponent of the electronic device.
 4. The method of claim 1, whereinthe input component is a biometric sensor.
 5. The method of claim 1,wherein the input component is a scanner.
 6. The method of claim 1,wherein the input component is a camera.
 7. The method of claim 1,wherein the input component is a button.
 8. The method of claim 1,further comprising: after the re-enabling, receiving authenticationinformation with the re-enabled input component; and enabling a nearfield communication component of the electronic device using thereceived authentication information.
 9. The method of claim 8, whereinthe enabling comprises activating an applet of a credential that isprovisioned on the near field communication component.
 10. The method ofclaim 8, wherein the input component is a biometric sensor.
 11. Themethod of claim 8, wherein the input component is at least one button.12. The method of claim 8, wherein the input component is a touchscreen.
 13. The method of claim 8, further comprising, after thedetection of the near field communication terminal but before thereceiving the authentication information, using an output component ofthe electronic device to request user authorization of the near fieldcommunication component.
 14. The method of claim 8, further comprising:in response to the detection of the low power mode initiation event,disabling an output component of the electronic device; and after thedetection of the near field communication terminal but before thereceiving the authentication information: re-enabling the outputcomponent of the electronic device; and requesting user authorization ofthe near field communication component with the re-enabled outputcomponent.
 15. A method of operating an electronic device comprising:detecting a low power mode initiation event; in response to thedetection of the low power mode initiation event, disabling an inputcomponent of the electronic device; while the input component isdisabled, identifying an authentication initiation event with theelectronic device; in response to the identification of theauthentication initiation event, re-enabling the input component of theelectronic device; after the re-enabling, receiving authenticationinformation with the re-enabled input component; and enabling a nearfield communication component of the electronic device using thereceived authentication information, wherein: the identifying theauthentication initiation event comprises receiving a user input withanother input component of the electronic device; the other inputcomponent is a button; and the input component is a biometric sensor.16. The method of claim 1, wherein the detecting the low power modeinitiation event comprises one of: receiving a user input on the inputcomponent of the electronic device; and detecting that a power level ofa power supply of the electronic device is below a particular threshold.17. An electronic device comprising: a near field communicationcomponent; an input component; and a processor configured to: detect alow power mode initiation event; disable the input component in responseto the detection of the low power mode initiation event; when the inputcomponent is disabled, detect a near field communication terminal withthe near field communication component; and in response to the detectionof the near field communication terminal with the electronic device,re-enable the input component.
 18. The electronic device of claim 17,wherein the processor is further configured to: receive authenticationinformation with the re-enabled input component; and enable a portion ofthe near field communication component of the electronic device usingthe received authentication information.
 19. A non-transitorycomputer-readable medium comprising computer-readable instructionsrecorded thereon for: detecting a low power mode initiation event on anelectronic device; and in response to the detecting the low power modeinitiation event: disabling an input component of the electronic device;detecting a near field communication terminal with the electronic devicewhile the input component is disabled; and in response to the detectingthe near field communication terminal, re-enabling the input component.